Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549b46e3c94fbcf67717a8e830b79f9e07c90f8896f22c8fae8ad13b3cc4d31e

Tx prefix hash: 0afa5f58767dd52ed95c1ac7526330ee6d7a19d32a52df62f6ee84386e321c95
Tx public key: 99af06b39339e741de30c0bacf5a568f0d78de216e9f6eb7ae17e06dc8bf4522
Timestamp: 1735985712 Timestamp [UCT]: 2025-01-04 10:15:12 Age [y:d:h:m:s]: 00:306:20:48:51
Block: 1189960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216808 RingCT/type: yes/0
Extra: 0199af06b39339e741de30c0bacf5a568f0d78de216e9f6eb7ae17e06dc8bf45220211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b004ce3d63ac12e3f08d908fa02e401dd67b2a9bf29053bd85917781ffbf825d 0.600000000000 1676475 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": 1189970, "vin": [ { "gen": { "height": 1189960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b004ce3d63ac12e3f08d908fa02e401dd67b2a9bf29053bd85917781ffbf825d" } } ], "extra": [ 1, 153, 175, 6, 179, 147, 57, 231, 65, 222, 48, 192, 186, 207, 90, 86, 143, 13, 120, 222, 33, 110, 159, 110, 183, 174, 23, 224, 109, 200, 191, 69, 34, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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