Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6954e5f27b37e0a6babc466d5e0f0ed1679926b2d8d1d27afa126597de8ac8c0

Tx prefix hash: 651797fd8f30f2bae303b912a05cb81bf3ab5f102185b4d9076cb1420ad6f9a7
Tx public key: 72f0a2a0b20e6f05ef3e7b3fee1643299fdf76bc8ae20f795be994d3dc2aff1f
Timestamp: 1711933174 Timestamp [UCT]: 2024-04-01 00:59:34 Age [y:d:h:m:s]: 01:009:07:28:40
Block: 990695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267599 RingCT/type: yes/0
Extra: 0172f0a2a0b20e6f05ef3e7b3fee1643299fdf76bc8ae20f795be994d3dc2aff1f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e57854be78943fb06486f63b8af0b4e46c0895b8eb0352780726789472fb8180 0.600000000000 1451021 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": 990705, "vin": [ { "gen": { "height": 990695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e57854be78943fb06486f63b8af0b4e46c0895b8eb0352780726789472fb8180" } } ], "extra": [ 1, 114, 240, 162, 160, 178, 14, 111, 5, 239, 62, 123, 63, 238, 22, 67, 41, 159, 223, 118, 188, 138, 226, 15, 121, 91, 233, 148, 211, 220, 42, 255, 31, 2, 17, 0, 0, 0, 3, 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