Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483e792620de5a9c25b9f453097830242c83f21d4b2f58ae045ddfa7f360df86

Tx prefix hash: 0e67c5376c1fe427acd1fb8cbceef5258f0794e08ec3e68d5df4e1b0e9b4a403
Tx public key: 077448d0e62ccc38c7e20cd3ee5fc9c677a60e2ff3a81ef1467bf70c5ec59e0a
Timestamp: 1737048236 Timestamp [UCT]: 2025-01-16 17:23:56 Age [y:d:h:m:s]: 00:152:02:07:43
Block: 1198745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108405 RingCT/type: yes/0
Extra: 01077448d0e62ccc38c7e20cd3ee5fc9c677a60e2ff3a81ef1467bf70c5ec59e0a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07b1e9b4644a4cad12e859e04aa2b1c4376a02c43a43e2fdcac60a0b1c5d1092 0.600000000000 1685372 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": 1198755, "vin": [ { "gen": { "height": 1198745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07b1e9b4644a4cad12e859e04aa2b1c4376a02c43a43e2fdcac60a0b1c5d1092" } } ], "extra": [ 1, 7, 116, 72, 208, 230, 44, 204, 56, 199, 226, 12, 211, 238, 95, 201, 198, 119, 166, 14, 47, 243, 168, 30, 241, 70, 123, 247, 12, 94, 197, 158, 10, 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