Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9e27ffedbf6ee21cb2610f2e61ba1b1a183812494a7fac0adf7be3d3758d2f

Tx prefix hash: 065703bc41bfddf7a4093fbb3473fbc36cbb1de1cbcdbc9f175f539ed592b1f9
Tx public key: abd6ea0907ec3f50a8f17787dc9c544e3729f3ded2a16700daef17aa949965d5
Timestamp: 1738305127 Timestamp [UCT]: 2025-01-31 06:32:07 Age [y:d:h:m:s]: 00:136:16:06:39
Block: 1208899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97641 RingCT/type: yes/0
Extra: 01abd6ea0907ec3f50a8f17787dc9c544e3729f3ded2a16700daef17aa949965d5021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f4e08903877f2b3c314a97b0ef34d2004a8d29c6e4c21d5ad647b7d67e548b 0.600000000000 1695634 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": 1208909, "vin": [ { "gen": { "height": 1208899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f4e08903877f2b3c314a97b0ef34d2004a8d29c6e4c21d5ad647b7d67e548b" } } ], "extra": [ 1, 171, 214, 234, 9, 7, 236, 63, 80, 168, 241, 119, 135, 220, 156, 84, 78, 55, 41, 243, 222, 210, 161, 103, 0, 218, 239, 23, 170, 148, 153, 101, 213, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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