Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d18b196a3484dd847c8109115d19c9729bc734e303292a76addbbeddc5cc6bf

Tx prefix hash: 63d5622801b2f69b5850c27dbdcc0d156e325627ddc0e8f2635faf3b7b59e176
Tx public key: 69162d9f3b60ccb84041c4fc85146781c1f2e6fcee65998d2c312e3829ce46e5
Timestamp: 1704664022 Timestamp [UCT]: 2024-01-07 21:47:02 Age [y:d:h:m:s]: 01:304:20:55:07
Block: 930392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476725 RingCT/type: yes/0
Extra: 0169162d9f3b60ccb84041c4fc85146781c1f2e6fcee65998d2c312e3829ce46e502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5786005b481186bd7bf398407fa12fdaacae2754c3da7215560887f5d3a665b9 0.600000000000 1388274 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": 930402, "vin": [ { "gen": { "height": 930392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5786005b481186bd7bf398407fa12fdaacae2754c3da7215560887f5d3a665b9" } } ], "extra": [ 1, 105, 22, 45, 159, 59, 96, 204, 184, 64, 65, 196, 252, 133, 20, 103, 129, 193, 242, 230, 252, 238, 101, 153, 141, 44, 49, 46, 56, 41, 206, 70, 229, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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