Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4131d0736eb1c940d6877f1ccb355f9f480f868d517888188f2c857292dac7b0

Tx prefix hash: 1a4dca2297a4945a5a0f603a9cf0a7ddce335761a5922882074d540d7702f6a6
Tx public key: 37b440848228117e8dc08148e5e96a84f5807295bfc0ad21752326c4ba01afdc
Timestamp: 1735167807 Timestamp [UCT]: 2024-12-25 23:03:27 Age [y:d:h:m:s]: 00:085:06:05:35
Block: 1183188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60718 RingCT/type: yes/0
Extra: 0137b440848228117e8dc08148e5e96a84f5807295bfc0ad21752326c4ba01afdc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa96e715380d493a9683a3a9de1e7b87fd2f155fab0261a5d7a87fb9352925ef 0.600000000000 1669629 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": 1183198, "vin": [ { "gen": { "height": 1183188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa96e715380d493a9683a3a9de1e7b87fd2f155fab0261a5d7a87fb9352925ef" } } ], "extra": [ 1, 55, 180, 64, 132, 130, 40, 17, 126, 141, 192, 129, 72, 229, 233, 106, 132, 245, 128, 114, 149, 191, 192, 173, 33, 117, 35, 38, 196, 186, 1, 175, 220, 2, 17, 0, 0, 0, 3, 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