Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0bd49cfd8e430f1575952ff31c5abd7d8a380d78302c3bb67eef12d37096ef

Tx prefix hash: d28d5e2fa275a35f6cd0ca62d7b331dd38e28190a2a720d3f7dad8b36ac1d85f
Tx public key: 29a21701f9c722078ad15689a987b3cffd695e4cc4ac6848678cf69b19f51ea7
Timestamp: 1728729751 Timestamp [UCT]: 2024-10-12 10:42:31 Age [y:d:h:m:s]: 01:032:17:13:12
Block: 1129931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281761 RingCT/type: yes/0
Extra: 0129a21701f9c722078ad15689a987b3cffd695e4cc4ac6848678cf69b19f51ea702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 883fd6b62e0b692a12712c191ebb6d2a0dbe838b676a25ae1a30a6bbcb81f416 0.600000000000 1612802 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": 1129941, "vin": [ { "gen": { "height": 1129931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "883fd6b62e0b692a12712c191ebb6d2a0dbe838b676a25ae1a30a6bbcb81f416" } } ], "extra": [ 1, 41, 162, 23, 1, 249, 199, 34, 7, 138, 209, 86, 137, 169, 135, 179, 207, 253, 105, 94, 76, 196, 172, 104, 72, 103, 140, 246, 155, 25, 245, 30, 167, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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