Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abc4d1a9f6067bc0fb187ffc1fa038dfcc894f31b73c697665bdf24f7b7a2cad

Tx prefix hash: c273e6ca4d7fa82b75f8fb963d0b55d686010eb8578acc97678eebd1b18dc194
Tx public key: 51a7528b3e6d52d3b55b9eefd69d0a9700e1310b2adf6bbd0649d38a413b95e5
Timestamp: 1722036828 Timestamp [UCT]: 2024-07-26 23:33:48 Age [y:d:h:m:s]: 00:288:01:53:44
Block: 1074436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205820 RingCT/type: yes/0
Extra: 0151a7528b3e6d52d3b55b9eefd69d0a9700e1310b2adf6bbd0649d38a413b95e502110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67024693e4a8e232308700441e7b20fa563671ee4633d769ce624dee738a7562 0.600000000000 1546949 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": 1074446, "vin": [ { "gen": { "height": 1074436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67024693e4a8e232308700441e7b20fa563671ee4633d769ce624dee738a7562" } } ], "extra": [ 1, 81, 167, 82, 139, 62, 109, 82, 211, 181, 91, 158, 239, 214, 157, 10, 151, 0, 225, 49, 11, 42, 223, 107, 189, 6, 73, 211, 138, 65, 59, 149, 229, 2, 17, 0, 0, 0, 11, 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