Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5063a6ffc517982258d0521ec795168569c0ef61ceaa685bceea9a60667ce594

Tx prefix hash: 35eea333af2ae0e16dde1d5d738814ea24e4911742575fc6a243cb3e73d33781
Tx public key: b16e447a54c3ecd602a6f726aad5373d01b665842541e9b0dc53dbee1a79717f
Timestamp: 1702930622 Timestamp [UCT]: 2023-12-18 20:17:02 Age [y:d:h:m:s]: 01:326:09:34:07
Block: 916041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492123 RingCT/type: yes/0
Extra: 01b16e447a54c3ecd602a6f726aad5373d01b665842541e9b0dc53dbee1a79717f021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3ae7dbcdc0bdd4809e9fa4d6e745f21ada23136fcd269078892db5148ed584 0.600000000000 1373511 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": 916051, "vin": [ { "gen": { "height": 916041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3ae7dbcdc0bdd4809e9fa4d6e745f21ada23136fcd269078892db5148ed584" } } ], "extra": [ 1, 177, 110, 68, 122, 84, 195, 236, 214, 2, 166, 247, 38, 170, 213, 55, 61, 1, 182, 101, 132, 37, 65, 233, 176, 220, 83, 219, 238, 26, 121, 113, 127, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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