Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbd61306b2bf1ce0a82b910ce59de85f78a0f0e53eca6454206749b5723e1d3f

Tx prefix hash: 844f5fcc498bc854945cb0a8db1f8fbc0853303d90a2f8730b2c870256f18195
Tx public key: 4489f98c0536aafb8bde7dd35883274afe6fc4e1a13e3424e57ab42fbd5818a6
Timestamp: 1704458727 Timestamp [UCT]: 2024-01-05 12:45:27 Age [y:d:h:m:s]: 01:080:15:16:35
Block: 928683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318738 RingCT/type: yes/0
Extra: 014489f98c0536aafb8bde7dd35883274afe6fc4e1a13e3424e57ab42fbd5818a60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e8d6765fe656e4e0d7396bf5d00ec4cfa222c508ce9d186e56274d0ca427fc 0.600000000000 1386543 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": 928693, "vin": [ { "gen": { "height": 928683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e8d6765fe656e4e0d7396bf5d00ec4cfa222c508ce9d186e56274d0ca427fc" } } ], "extra": [ 1, 68, 137, 249, 140, 5, 54, 170, 251, 139, 222, 125, 211, 88, 131, 39, 74, 254, 111, 196, 225, 161, 62, 52, 36, 229, 122, 180, 47, 189, 88, 24, 166, 2, 17, 0, 0, 0, 2, 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