Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a74171977cb79f967ad882f44848e76c7613b664eafe6694a13ed28a77073179

Tx prefix hash: f2afe737094679a85877449cbcaaa7a7ddcfdd7852b4540c76e6fac006d7491a
Tx public key: 11e8f8fe1e931d30af6fd1460cbdd9f1767daa1d4e4ff399df8047b09b0c50e3
Timestamp: 1649959636 Timestamp [UCT]: 2022-04-14 18:07:16 Age [y:d:h:m:s]: 03:204:11:43:00
Block: 480172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 924412 RingCT/type: yes/0
Extra: 0111e8f8fe1e931d30af6fd1460cbdd9f1767daa1d4e4ff399df8047b09b0c50e3021100000032cb8520c2000000000000000000

1 output(s) for total of 15.739504993000 dcy

stealth address amount amount idx
00: 8328eab39c652182403498a11972d6ca4350f1600e7c3956f5c1747746651a64 15.739504993000 901177 of 0

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": 480182, "vin": [ { "gen": { "height": 480172 } } ], "vout": [ { "amount": 15739504993, "target": { "key": "8328eab39c652182403498a11972d6ca4350f1600e7c3956f5c1747746651a64" } } ], "extra": [ 1, 17, 232, 248, 254, 30, 147, 29, 48, 175, 111, 209, 70, 12, 189, 217, 241, 118, 125, 170, 29, 78, 79, 243, 153, 223, 128, 71, 176, 155, 12, 80, 227, 2, 17, 0, 0, 0, 50, 203, 133, 32, 194, 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