Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ab0c24db723eac2c874d4d1bb4053adae79eef2a02a622d844d4d9cb151cab8

Tx prefix hash: 274fbc0e8569ee15aa742a26ac3130ccc06fe3e40a231347e45b1d185035ed32
Tx public key: 93fa1b889d3117a4f448aef83c6c8b00e414b555afa0f82adf83325f29e5d590
Timestamp: 1737890486 Timestamp [UCT]: 2025-01-26 11:21:26 Age [y:d:h:m:s]: 00:142:03:00:21
Block: 1205677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101331 RingCT/type: yes/0
Extra: 0193fa1b889d3117a4f448aef83c6c8b00e414b555afa0f82adf83325f29e5d590021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1398473917c1f4e0fa19a18d45d938f8657c7bdcae47122fce23a9af784d587d 0.600000000000 1692376 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": 1205687, "vin": [ { "gen": { "height": 1205677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1398473917c1f4e0fa19a18d45d938f8657c7bdcae47122fce23a9af784d587d" } } ], "extra": [ 1, 147, 250, 27, 136, 157, 49, 23, 164, 244, 72, 174, 248, 60, 108, 139, 0, 228, 20, 181, 85, 175, 160, 248, 42, 223, 131, 50, 95, 41, 229, 213, 144, 2, 17, 0, 0, 0, 5, 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