Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7403d728281cdb7036e123b2900b5a9b920a8367ddd86af207aaa09257d6704a

Tx prefix hash: 509664f2a695a7fd66fedf3c956ee24b3c00c3dc2405e1506a836541bafdaa26
Tx public key: e2a0bc2430cabb2d2fc1ecf8fc2e16bb791337691f5591a529c7a31fd7aedc84
Timestamp: 1726948531 Timestamp [UCT]: 2024-09-21 19:55:31 Age [y:d:h:m:s]: 00:208:22:02:51
Block: 1115163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149142 RingCT/type: yes/0
Extra: 01e2a0bc2430cabb2d2fc1ecf8fc2e16bb791337691f5591a529c7a31fd7aedc8402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7f208279d692bfdd533d4d34c73925182a608140c35440ca677ff6e816d0393 0.600000000000 1595202 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": 1115173, "vin": [ { "gen": { "height": 1115163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f208279d692bfdd533d4d34c73925182a608140c35440ca677ff6e816d0393" } } ], "extra": [ 1, 226, 160, 188, 36, 48, 202, 187, 45, 47, 193, 236, 248, 252, 46, 22, 187, 121, 19, 55, 105, 31, 85, 145, 165, 41, 199, 163, 31, 215, 174, 220, 132, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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