Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa48c22a79e40d612e1f3b286a44aa8e875fb5b185c889c0c7adebe86533ff8

Tx prefix hash: f298a8026b4cf7e29a135ca49a98b700391dcac1f1e3a28df41f9818ed6315a9
Tx public key: 44690e46b942db2aa39532cdfedb1c2b2901b76684f77d6ffb408991049820b9
Timestamp: 1698357748 Timestamp [UCT]: 2023-10-26 22:02:28 Age [y:d:h:m:s]: 01:162:06:02:15
Block: 878351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376947 RingCT/type: yes/0
Extra: 0144690e46b942db2aa39532cdfedb1c2b2901b76684f77d6ffb408991049820b9021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.754498762000 dcy

stealth address amount amount idx
00: 8152f674c2d194c2bb62e2fc5b3b5ec8e07840d1b83b837481619ad800756530 0.754498762000 1333789 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": 878361, "vin": [ { "gen": { "height": 878351 } } ], "vout": [ { "amount": 754498762, "target": { "key": "8152f674c2d194c2bb62e2fc5b3b5ec8e07840d1b83b837481619ad800756530" } } ], "extra": [ 1, 68, 105, 14, 70, 185, 66, 219, 42, 163, 149, 50, 205, 254, 219, 28, 43, 41, 1, 183, 102, 132, 247, 125, 111, 251, 64, 137, 145, 4, 152, 32, 185, 2, 17, 0, 0, 0, 6, 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