Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea29e5b789f34f22facaee1f8613f9e3dafcc8a79200a4ab5c0b526a24e2d69a

Tx prefix hash: 03dd1999f44f79da561585a889977d1a9c3b4736447c5f5b4673a7e4568e71e8
Tx public key: ebf007a244b8ab2213d8e662aa0ddca28cd9aa263124c26787c9c76c3471e788
Timestamp: 1725127806 Timestamp [UCT]: 2024-08-31 18:10:06 Age [y:d:h:m:s]: 00:217:01:25:57
Block: 1100059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154989 RingCT/type: yes/0
Extra: 01ebf007a244b8ab2213d8e662aa0ddca28cd9aa263124c26787c9c76c3471e78802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5d975f2d5375b421c4e64ccf4dda5593151c398a503f7fc992301937e15803 0.600000000000 1576032 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": 1100069, "vin": [ { "gen": { "height": 1100059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5d975f2d5375b421c4e64ccf4dda5593151c398a503f7fc992301937e15803" } } ], "extra": [ 1, 235, 240, 7, 162, 68, 184, 171, 34, 19, 216, 230, 98, 170, 13, 220, 162, 140, 217, 170, 38, 49, 36, 194, 103, 135, 201, 199, 108, 52, 113, 231, 136, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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