Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97f33561c82916c9ffab757a656e95f5cb0c1028568ad03c7b8e3300313d7ce

Tx prefix hash: 75ba93b26d5fb9f33d19320fbe457c28d6bdf02ef1c90f288eb32df8b1983e85
Tx public key: 9973480be8e39db358c407b8b38c180e147ddd0fef603d72825e54e5e83b7f23
Timestamp: 1750998389 Timestamp [UCT]: 2025-06-27 04:26:29 Age [y:d:h:m:s]: 00:191:00:33:37
Block: 1313629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134616 RingCT/type: yes/0
Extra: 019973480be8e39db358c407b8b38c180e147ddd0fef603d72825e54e5e83b7f23021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4aaf2a504b247e82775e28a8e9ca13b05c1de952e6317224d9471b921d83b59 0.600000000000 1801270 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": 1313639, "vin": [ { "gen": { "height": 1313629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4aaf2a504b247e82775e28a8e9ca13b05c1de952e6317224d9471b921d83b59" } } ], "extra": [ 1, 153, 115, 72, 11, 232, 227, 157, 179, 88, 196, 7, 184, 179, 140, 24, 14, 20, 125, 221, 15, 239, 96, 61, 114, 130, 94, 84, 229, 232, 59, 127, 35, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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