Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70bb65d71c24a1f9f6afcad83fbe333b0e6e0ce97fe86fa6dffff465bb9ed2fa

Tx prefix hash: cc43e441e822e940964482f464e30b817c3ace1b54893c3d44f72fc48ec2f124
Tx public key: 6551f6c2dd9c0d83001f2a1e0ad7b9df96c5a387e3d27341a353f610b9f17f7e
Timestamp: 1702362625 Timestamp [UCT]: 2023-12-12 06:30:25 Age [y:d:h:m:s]: 01:193:03:32:05
Block: 911340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399038 RingCT/type: yes/0
Extra: 016551f6c2dd9c0d83001f2a1e0ad7b9df96c5a387e3d27341a353f610b9f17f7e021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28619f573517c1fc24c192b51d38bc0fc45b7e3a951b530afbcfe19201c8003a 0.600000000000 1368525 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": 911350, "vin": [ { "gen": { "height": 911340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28619f573517c1fc24c192b51d38bc0fc45b7e3a951b530afbcfe19201c8003a" } } ], "extra": [ 1, 101, 81, 246, 194, 221, 156, 13, 131, 0, 31, 42, 30, 10, 215, 185, 223, 150, 197, 163, 135, 227, 210, 115, 65, 163, 83, 246, 16, 185, 241, 127, 126, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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