Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8c3fb961d5b576ace5ae47cc7b06a3436b35838016a9b709a8db1de2a5bdaf19

Tx prefix hash: 7b4d170871114cc9c8a3e0e5760bb671f47bf6dcc36fc6bcfd73265aada93af0
Tx public key: ffb17e30bfccdf3024e25f3f72cf66850d37d2a5de4cb6342ea8f2f9ecb910bb
Timestamp: 1704475261 Timestamp [UCT]: 2024-01-05 17:21:01 Age [y:d:h:m:s]: 01:089:13:19:44
Block: 928831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325120 RingCT/type: yes/0
Extra: 01ffb17e30bfccdf3024e25f3f72cf66850d37d2a5de4cb6342ea8f2f9ecb910bb02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4ea1c4321d60a94a6f9beb97bab6ae3c054989329bedaa3fb4ebd2744d363a8 0.600000000000 1386695 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 928841, "vin": [ { "gen": { "height": 928831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4ea1c4321d60a94a6f9beb97bab6ae3c054989329bedaa3fb4ebd2744d363a8" } } ], "extra": [ 1, 255, 177, 126, 48, 191, 204, 223, 48, 36, 226, 95, 63, 114, 207, 102, 133, 13, 55, 210, 165, 222, 76, 182, 52, 46, 168, 242, 249, 236, 185, 16, 187, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8