Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258e2cb207c9d088d939ab4d5896606d81ece7fc4c0caaa7a8003495670f6172

Tx prefix hash: 4136ab9d2c26e2e6d6e844a2905f1921962f01087ed6a95d0b2074e74edeeb62
Tx public key: da564e24a9fca1ff9a6a9bdc0ed54faf81a670e5859d698681e6223bcbdba2b0
Timestamp: 1723461102 Timestamp [UCT]: 2024-08-12 11:11:42 Age [y:d:h:m:s]: 00:217:01:08:43
Block: 1086253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155012 RingCT/type: yes/0
Extra: 01da564e24a9fca1ff9a6a9bdc0ed54faf81a670e5859d698681e6223bcbdba2b002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56a7bfce3949c9e00976c069d5bb1541a913608cd4c6da05cb80bdca953c08ab 0.600000000000 1560848 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": 1086263, "vin": [ { "gen": { "height": 1086253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56a7bfce3949c9e00976c069d5bb1541a913608cd4c6da05cb80bdca953c08ab" } } ], "extra": [ 1, 218, 86, 78, 36, 169, 252, 161, 255, 154, 106, 155, 220, 14, 213, 79, 175, 129, 166, 112, 229, 133, 157, 105, 134, 129, 230, 34, 59, 203, 219, 162, 176, 2, 17, 0, 0, 0, 1, 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