Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93180e2e6dd566b94e697ddfc212506e8a9755e8a6d92eea8e25d34a9b5f4331

Tx prefix hash: 27704930764660a953b482c26c7edaa9ae37f2943cbca83b5bbd2e813c2e2b4f
Tx public key: a0ccd0fcb861507fff9ec4213e56c2c8e5130958df5d25a85ec5a1bc6b65dfc9
Timestamp: 1705883286 Timestamp [UCT]: 2024-01-22 00:28:06 Age [y:d:h:m:s]: 01:290:21:34:01
Block: 940494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466725 RingCT/type: yes/0
Extra: 01a0ccd0fcb861507fff9ec4213e56c2c8e5130958df5d25a85ec5a1bc6b65dfc902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88e6ef359db492ccd91a59069acfeb68ecec49bf447c913e7c6ca05864edf4d 0.600000000000 1398632 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": 940504, "vin": [ { "gen": { "height": 940494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88e6ef359db492ccd91a59069acfeb68ecec49bf447c913e7c6ca05864edf4d" } } ], "extra": [ 1, 160, 204, 208, 252, 184, 97, 80, 127, 255, 158, 196, 33, 62, 86, 194, 200, 229, 19, 9, 88, 223, 93, 37, 168, 94, 197, 161, 188, 107, 101, 223, 201, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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