Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9c8fdf1652e13177185e9758741e3947ae7ae1426e96f7a7357da97a4adee70

Tx prefix hash: 03bc3318e50f774ffdbce211badbe6f22decfe3d4517650e80cbe7c5f0683dd4
Tx public key: 507ef5430fed3ea3f0ea90a2f81dad92092dc9f7b47782e461554cc3c63294f2
Timestamp: 1732581561 Timestamp [UCT]: 2024-11-26 00:39:21 Age [y:d:h:m:s]: 00:131:17:03:37
Block: 1161760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93938 RingCT/type: yes/0
Extra: 01507ef5430fed3ea3f0ea90a2f81dad92092dc9f7b47782e461554cc3c63294f20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e83ea13f5d47273c5ab5e21a076649b19b1cd95d322c99d8a26a7d2807abcdb 0.600000000000 1647415 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": 1161770, "vin": [ { "gen": { "height": 1161760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e83ea13f5d47273c5ab5e21a076649b19b1cd95d322c99d8a26a7d2807abcdb" } } ], "extra": [ 1, 80, 126, 245, 67, 15, 237, 62, 163, 240, 234, 144, 162, 248, 29, 173, 146, 9, 45, 201, 247, 180, 119, 130, 228, 97, 85, 76, 195, 198, 50, 148, 242, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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