Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202903cef5c5d776d972168186c52aced19d00770f863dc043e007d88a30df7f

Tx prefix hash: 5a3b3b8808e9fa1d1218ef093d36309441d72bc4d44af35111c6c90fa1232498
Tx public key: 3f80fe016febffd6507921f0d66736e5a4aad386714597273d8dcb3e8a673e67
Timestamp: 1696763746 Timestamp [UCT]: 2023-10-08 11:15:46 Age [y:d:h:m:s]: 01:164:15:07:13
Block: 865124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378700 RingCT/type: yes/0
Extra: 013f80fe016febffd6507921f0d66736e5a4aad386714597273d8dcb3e8a673e6702110000000675e3f0e9000000000000000000

1 output(s) for total of 0.834612899000 dcy

stealth address amount amount idx
00: a61d7fc1102eb57ab2c7b76956235bbb02e9c678db2aa2ddf9018eaf9eae1d0e 0.834612899000 1319650 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": 865134, "vin": [ { "gen": { "height": 865124 } } ], "vout": [ { "amount": 834612899, "target": { "key": "a61d7fc1102eb57ab2c7b76956235bbb02e9c678db2aa2ddf9018eaf9eae1d0e" } } ], "extra": [ 1, 63, 128, 254, 1, 111, 235, 255, 214, 80, 121, 33, 240, 214, 103, 54, 229, 164, 170, 211, 134, 113, 69, 151, 39, 61, 141, 203, 62, 138, 103, 62, 103, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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