Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41d1c2f8c0b898650dd458efe5a75d94ec5171fb9a182af7590e2c2f26d1d7de

Tx prefix hash: 229ca29647c1a46825d86e56b332dc0bc43d1edea57be8945f9ac2edb56c2dee
Tx public key: de41fa54ad4a67a024391f7242eb26623f3317846dc5ca1296e5546c5f7d1335
Timestamp: 1723556410 Timestamp [UCT]: 2024-08-13 13:40:10 Age [y:d:h:m:s]: 00:277:22:22:04
Block: 1087040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198541 RingCT/type: yes/0
Extra: 01de41fa54ad4a67a024391f7242eb26623f3317846dc5ca1296e5546c5f7d1335021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fac7834678e908df7e9b7421686d5ec26e6c9c0e0af8abddd81d456ee232f39 0.600000000000 1561643 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": 1087050, "vin": [ { "gen": { "height": 1087040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fac7834678e908df7e9b7421686d5ec26e6c9c0e0af8abddd81d456ee232f39" } } ], "extra": [ 1, 222, 65, 250, 84, 173, 74, 103, 160, 36, 57, 31, 114, 66, 235, 38, 98, 63, 51, 23, 132, 109, 197, 202, 18, 150, 229, 84, 108, 95, 125, 19, 53, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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