Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d33483da1374d84fd361dff267d037ddc86266bc63cb8e888361e1f31f1a48b0

Tx prefix hash: 167856039afc7f6492bd308b0b64e7fabc23ee6eb76786383d37530428c081d5
Tx public key: 310110034f7ba16fe4f6ecfbb3f57eb82dab806715e4b5e3b2b1e89a117cb1e4
Timestamp: 1733752964 Timestamp [UCT]: 2024-12-09 14:02:44 Age [y:d:h:m:s]: 00:190:05:44:56
Block: 1171479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135674 RingCT/type: yes/0
Extra: 01310110034f7ba16fe4f6ecfbb3f57eb82dab806715e4b5e3b2b1e89a117cb1e4021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1872fdbbfd1b140f8b95e03b50e2b7ffcbb5521a5270ae191848677b7cdf5371 0.600000000000 1657242 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": 1171489, "vin": [ { "gen": { "height": 1171479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1872fdbbfd1b140f8b95e03b50e2b7ffcbb5521a5270ae191848677b7cdf5371" } } ], "extra": [ 1, 49, 1, 16, 3, 79, 123, 161, 111, 228, 246, 236, 251, 179, 245, 126, 184, 45, 171, 128, 103, 21, 228, 181, 227, 178, 177, 232, 154, 17, 124, 177, 228, 2, 17, 0, 0, 0, 4, 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