Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1cb173969fa782916028be9637d06c6dff0cf59d9b2b0be09927d3d2a7d8313

Tx prefix hash: 91ce7290197e37a5c5f4daa021a19691a6fe36161f473b18a6fdc0ac19abe908
Tx public key: 7c861242ec3041e921f53c15cce134fb459d1abe982de797e04d6a125d7601f5
Timestamp: 1702061374 Timestamp [UCT]: 2023-12-08 18:49:34 Age [y:d:h:m:s]: 02:015:23:39:56
Block: 908828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531210 RingCT/type: yes/0
Extra: 017c861242ec3041e921f53c15cce134fb459d1abe982de797e04d6a125d7601f502110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fc0b30e4a5c8160e762adba069b9c9e0a0b366a16c5f5a9a79972b0097c5359 0.600000000000 1365885 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": 908838, "vin": [ { "gen": { "height": 908828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fc0b30e4a5c8160e762adba069b9c9e0a0b366a16c5f5a9a79972b0097c5359" } } ], "extra": [ 1, 124, 134, 18, 66, 236, 48, 65, 233, 33, 245, 60, 21, 204, 225, 52, 251, 69, 157, 26, 190, 152, 45, 231, 151, 224, 77, 106, 18, 93, 118, 1, 245, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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