Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a66291207d46502500288c1e292a37a9e559d67dbd95e723f90da95bb0acd1

Tx prefix hash: 2d347ef24f83a6571b7053bae1ed42a3b44bb62d29b78ad4ed5833ae11de0f6e
Tx public key: d32fa736f37c2cb5c195fbbea20a3b928e594a3d68653322573d278e77d0c3fc
Timestamp: 1710630467 Timestamp [UCT]: 2024-03-16 23:07:47 Age [y:d:h:m:s]: 01:039:13:55:11
Block: 979893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289271 RingCT/type: yes/0
Extra: 01d32fa736f37c2cb5c195fbbea20a3b928e594a3d68653322573d278e77d0c3fc021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea471e1c7426019570c980f814d602635a44b248bc384edbf5d92a2bff961f8d 0.600000000000 1439948 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": 979903, "vin": [ { "gen": { "height": 979893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea471e1c7426019570c980f814d602635a44b248bc384edbf5d92a2bff961f8d" } } ], "extra": [ 1, 211, 47, 167, 54, 243, 124, 44, 181, 193, 149, 251, 190, 162, 10, 59, 146, 142, 89, 74, 61, 104, 101, 51, 34, 87, 61, 39, 142, 119, 208, 195, 252, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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