Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d1ba2651334c9cd4ab0b326374ef4ab107698b03bf30c11dbe857384e387334

Tx prefix hash: 935337e3e3c7291c6cf5bd478d91fc90a53d9a9c8f0b0ef1c91daef6123f0ac5
Tx public key: d17d432c9d450a5fb5a1596e4cfc2fa6ac61ce6b3ac2b82237e0f00bd7c3a783
Timestamp: 1710685291 Timestamp [UCT]: 2024-03-17 14:21:31 Age [y:d:h:m:s]: 00:342:16:57:38
Block: 980350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244985 RingCT/type: yes/0
Extra: 01d17d432c9d450a5fb5a1596e4cfc2fa6ac61ce6b3ac2b82237e0f00bd7c3a78302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 458e8e5b6a31257c54466985005bb1c3387054d2c1387a1f7a549d937e50d07c 0.600000000000 1440415 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": 980360, "vin": [ { "gen": { "height": 980350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "458e8e5b6a31257c54466985005bb1c3387054d2c1387a1f7a549d937e50d07c" } } ], "extra": [ 1, 209, 125, 67, 44, 157, 69, 10, 95, 181, 161, 89, 110, 76, 252, 47, 166, 172, 97, 206, 107, 58, 194, 184, 34, 55, 224, 240, 11, 215, 195, 167, 131, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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