Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01f28c24b264c99798ee76133c79be7986cf13090b3164a8bbde5831b74601d1

Tx prefix hash: 47a71da77e1979e8f1acd3d29cc53a8cf2c5aab3ed5b3345b7579df09e9330b4
Tx public key: ee67ce492c15460a693618f90af2b7ee15e8f8cc3feb8f0c45bb2236520b5ab9
Timestamp: 1699206514 Timestamp [UCT]: 2023-11-05 17:48:34 Age [y:d:h:m:s]: 01:153:20:09:37
Block: 885161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371143 RingCT/type: yes/0
Extra: 01ee67ce492c15460a693618f90af2b7ee15e8f8cc3feb8f0c45bb2236520b5ab902110000000233af99f4000000000000000000

1 output(s) for total of 0.716298702000 dcy

stealth address amount amount idx
00: b30c08382b4b55a078a98cd619c8c499a969ca59c63f124c4024a3d869f5b616 0.716298702000 1340916 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": 885171, "vin": [ { "gen": { "height": 885161 } } ], "vout": [ { "amount": 716298702, "target": { "key": "b30c08382b4b55a078a98cd619c8c499a969ca59c63f124c4024a3d869f5b616" } } ], "extra": [ 1, 238, 103, 206, 73, 44, 21, 70, 10, 105, 54, 24, 249, 10, 242, 183, 238, 21, 232, 248, 204, 63, 235, 143, 12, 69, 187, 34, 54, 82, 11, 90, 185, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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