Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2074dcf16fd36d30b066accf7bf0385f7088961d61c4b557205bb08d67c3f250

Tx prefix hash: 37fe2d1c9540c5f83e5001cbd5c3f5e9504880d820124ae6c05e1b635985d4bd
Tx public key: 5dc65933db2a66beb32b6a3e4926d1924f1d5f9096924b27dc4531d05213b260
Timestamp: 1734208219 Timestamp [UCT]: 2024-12-14 20:30:19 Age [y:d:h:m:s]: 00:188:10:24:06
Block: 1175260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134329 RingCT/type: yes/0
Extra: 015dc65933db2a66beb32b6a3e4926d1924f1d5f9096924b27dc4531d05213b2600211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76c5dbb294d2a2d6685ab61395222c9f75d2ee3299828452640a6dc29bca4776 0.600000000000 1661515 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": 1175270, "vin": [ { "gen": { "height": 1175260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76c5dbb294d2a2d6685ab61395222c9f75d2ee3299828452640a6dc29bca4776" } } ], "extra": [ 1, 93, 198, 89, 51, 219, 42, 102, 190, 179, 43, 106, 62, 73, 38, 209, 146, 79, 29, 95, 144, 150, 146, 75, 39, 220, 69, 49, 208, 82, 19, 178, 96, 2, 17, 0, 0, 0, 4, 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