Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2684ea7e68f4fcdc75a4fc33f3ac22ad18d304184496213c7ce9156f352fef64

Tx prefix hash: b260b623045dab119c9a8d5de8a678b11f60e76cb110a8cd7d44cc018e8191e4
Tx public key: 652b4df3b78bb5d30ff4c0ba94d1667c29c723398ff07409e6c93d9b01e778f3
Timestamp: 1733215914 Timestamp [UCT]: 2024-12-03 08:51:54 Age [y:d:h:m:s]: 00:164:17:46:56
Block: 1167021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117569 RingCT/type: yes/0
Extra: 01652b4df3b78bb5d30ff4c0ba94d1667c29c723398ff07409e6c93d9b01e778f3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c8e2c46746ea16bd98253bb7dda9ef7a67918d213453453865b782f3c40256f 0.600000000000 1652714 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": 1167031, "vin": [ { "gen": { "height": 1167021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c8e2c46746ea16bd98253bb7dda9ef7a67918d213453453865b782f3c40256f" } } ], "extra": [ 1, 101, 43, 77, 243, 183, 139, 181, 211, 15, 244, 192, 186, 148, 209, 102, 124, 41, 199, 35, 57, 143, 240, 116, 9, 230, 201, 61, 155, 1, 231, 120, 243, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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