Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5656c8ecdb51015e64bd22c4a05125afce0a06fe27118088a28defa173f49b7

Tx prefix hash: 5f9c5a0feffcb0011955a3aa5442ebd7343975b4f1c760972540e668bca1dc76
Tx public key: f001bccac81c1cec0c3e236df64d05c59af60a8d67d4a478551bf5b8cd789d2c
Timestamp: 1705171196 Timestamp [UCT]: 2024-01-13 18:39:56 Age [y:d:h:m:s]: 01:299:05:58:36
Block: 934596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472697 RingCT/type: yes/0
Extra: 01f001bccac81c1cec0c3e236df64d05c59af60a8d67d4a478551bf5b8cd789d2c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 968f35ebc0bcf97335981689bed93721e557857d7acbd138839a170886b85a71 0.600000000000 1392610 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": 934606, "vin": [ { "gen": { "height": 934596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "968f35ebc0bcf97335981689bed93721e557857d7acbd138839a170886b85a71" } } ], "extra": [ 1, 240, 1, 188, 202, 200, 28, 28, 236, 12, 62, 35, 109, 246, 77, 5, 197, 154, 246, 10, 141, 103, 212, 164, 120, 85, 27, 245, 184, 205, 120, 157, 44, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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