Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 331b97e5936eccdec49fd225c084430f466f9c14c141b63be9bceeb1d3da15ce

Tx prefix hash: bf7a12fef4e85d0cd67d226a86d2afd0d15b8c2c8fbfcbbba45cb719b3002e6a
Tx public key: 4dbc487ce86f2069b78609f87579a70f3749c9e8e2e4b3eca45bb01dad1385ed
Timestamp: 1711988463 Timestamp [UCT]: 2024-04-01 16:21:03 Age [y:d:h:m:s]: 01:056:00:52:42
Block: 991105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301075 RingCT/type: yes/0
Extra: 014dbc487ce86f2069b78609f87579a70f3749c9e8e2e4b3eca45bb01dad1385ed02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa2d66fdbc57578406f0fccf2a2ea865d500921cbc9688261351434492e324d 0.600000000000 1451439 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": 991115, "vin": [ { "gen": { "height": 991105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa2d66fdbc57578406f0fccf2a2ea865d500921cbc9688261351434492e324d" } } ], "extra": [ 1, 77, 188, 72, 124, 232, 111, 32, 105, 183, 134, 9, 248, 117, 121, 167, 15, 55, 73, 201, 232, 226, 228, 179, 236, 164, 91, 176, 29, 173, 19, 133, 237, 2, 17, 0, 0, 0, 10, 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