Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d70ad35922514d674d2188bb6be5f8aa4eede80be76c096688b81ba70570e81c

Tx prefix hash: 37dd12b767dfd7bc8e3d9d120d6a7c32baaf676268b9669186428bea680541e6
Tx public key: 38850abb7a4e9816e327da2d2a071a66ca6c1ce99fd778432d5069edeef39ec7
Timestamp: 1725899932 Timestamp [UCT]: 2024-09-09 16:38:52 Age [y:d:h:m:s]: 00:233:22:49:51
Block: 1106471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167060 RingCT/type: yes/0
Extra: 0138850abb7a4e9816e327da2d2a071a66ca6c1ce99fd778432d5069edeef39ec7021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b716ae90e6f5b0a8f86d0fd9b5b4b4077822ca6e30f73cace4388e21c17fb3d 0.600000000000 1584070 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": 1106481, "vin": [ { "gen": { "height": 1106471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b716ae90e6f5b0a8f86d0fd9b5b4b4077822ca6e30f73cace4388e21c17fb3d" } } ], "extra": [ 1, 56, 133, 10, 187, 122, 78, 152, 22, 227, 39, 218, 45, 42, 7, 26, 102, 202, 108, 28, 233, 159, 215, 120, 67, 45, 80, 105, 237, 238, 243, 158, 199, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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