Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07c850023ba05af40ff273767af4d237f08202ffb7e4569351090a6cc28441a7

Tx prefix hash: 3bb011c615c92a5dd7be511843b331e1ddc26827dc0ad76e288c33cd1af8c643
Tx public key: 2f730bbf37d8d89fe5e50543cb6f7f4ed17e5cb2e85b1d717c95325c79c8000a
Timestamp: 1762450732 Timestamp [UCT]: 2025-11-06 17:38:52 Age [y:d:h:m:s]: 00:086:16:27:26
Block: 1406354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61901 RingCT/type: yes/0
Extra: 012f730bbf37d8d89fe5e50543cb6f7f4ed17e5cb2e85b1d717c95325c79c8000a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb1ec4152c548d53267826163a7eaaf52ad029ca3eb7bc25802d039558b784a2 0.600000000000 1894737 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": 1406364, "vin": [ { "gen": { "height": 1406354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb1ec4152c548d53267826163a7eaaf52ad029ca3eb7bc25802d039558b784a2" } } ], "extra": [ 1, 47, 115, 11, 191, 55, 216, 216, 159, 229, 229, 5, 67, 203, 111, 127, 78, 209, 126, 92, 178, 232, 91, 29, 113, 124, 149, 50, 92, 121, 200, 0, 10, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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