Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3387132a89ef02902b7ca46783296955c9e138cb7650e0009134bb702257381f

Tx prefix hash: 467b3d97bc38edad9746aaf18c7ac7fd6a1d2634ceb60d18882cde6d1272c13d
Tx public key: 10ad408e4b9cdf34be0b51e6e1f5671804a4b1133c3a9006eee3db81e915af12
Timestamp: 1730844104 Timestamp [UCT]: 2024-11-05 22:01:44 Age [y:d:h:m:s]: 00:077:15:05:03
Block: 1147363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55513 RingCT/type: yes/0
Extra: 0110ad408e4b9cdf34be0b51e6e1f5671804a4b1133c3a9006eee3db81e915af120211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368eb74f29e8812f0cb611bfee18c8df1556a44dc04ce8e1a0904e8f8cb9f3b1 0.600000000000 1632058 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": 1147373, "vin": [ { "gen": { "height": 1147363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368eb74f29e8812f0cb611bfee18c8df1556a44dc04ce8e1a0904e8f8cb9f3b1" } } ], "extra": [ 1, 16, 173, 64, 142, 75, 156, 223, 52, 190, 11, 81, 230, 225, 245, 103, 24, 4, 164, 177, 19, 60, 58, 144, 6, 238, 227, 219, 129, 233, 21, 175, 18, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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