Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438c55441980180069cc3eb659b7f5b070dd85260f286861bee7c7abfd8f744a

Tx prefix hash: 820bc49d23ab8027ccab757b81ab3f06a779b022daa809561c595b2fcdcb6ad3
Tx public key: 7ea535e8feb29cdf8f645f1acf3e32c0ad57b7e62873736451d3df7c83997a4b
Timestamp: 1717419432 Timestamp [UCT]: 2024-06-03 12:57:12 Age [y:d:h:m:s]: 00:304:07:27:20
Block: 1036176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217463 RingCT/type: yes/0
Extra: 017ea535e8feb29cdf8f645f1acf3e32c0ad57b7e62873736451d3df7c83997a4b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a7d3e768e674f44256b74111116d3213a50160fa5d00e3b66962da243b27140 0.600000000000 1504701 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": 1036186, "vin": [ { "gen": { "height": 1036176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a7d3e768e674f44256b74111116d3213a50160fa5d00e3b66962da243b27140" } } ], "extra": [ 1, 126, 165, 53, 232, 254, 178, 156, 223, 143, 100, 95, 26, 207, 62, 50, 192, 173, 87, 183, 230, 40, 115, 115, 100, 81, 211, 223, 124, 131, 153, 122, 75, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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