Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4546f98a65ffd6c89441ffc15155e17f4ec48d639dfecfbdf1d02cb55f1c3b91

Tx prefix hash: b2492009800d18d65ee3d0d5282852f4d1de8852a73c9fb4fbd7c1e643bb17c7
Tx public key: fe2296d95b43f266e2ce46a11704939bbb7a787f0c2a3adaa9ee5d7822e19118
Timestamp: 1713769130 Timestamp [UCT]: 2024-04-22 06:58:50 Age [y:d:h:m:s]: 01:195:07:27:15
Block: 1005892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398228 RingCT/type: yes/0
Extra: 01fe2296d95b43f266e2ce46a11704939bbb7a787f0c2a3adaa9ee5d7822e1911802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39a92e57575a74c3df30a699ff346dddf04e14b6ca1e344f6d2dfcf46ce66c40 0.600000000000 1466732 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": 1005902, "vin": [ { "gen": { "height": 1005892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39a92e57575a74c3df30a699ff346dddf04e14b6ca1e344f6d2dfcf46ce66c40" } } ], "extra": [ 1, 254, 34, 150, 217, 91, 67, 242, 102, 226, 206, 70, 161, 23, 4, 147, 155, 187, 122, 120, 127, 12, 42, 58, 218, 169, 238, 93, 120, 34, 225, 145, 24, 2, 17, 0, 0, 0, 4, 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