Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b0598d4adaaac14bd0d536235baf4a356115b387b27f611fe394cce212f13ec

Tx prefix hash: 1153e6dd808dc1f30e81499cb8abca9ffdfe467fe63e4a9108dedaa8336c611e
Tx public key: b66975d5466d635f4e930fa27a1b13efa51aa4d4d706e5630edc83c179c9abae
Timestamp: 1720169570 Timestamp [UCT]: 2024-07-05 08:52:50 Age [y:d:h:m:s]: 00:267:01:44:07
Block: 1058957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190822 RingCT/type: yes/0
Extra: 01b66975d5466d635f4e930fa27a1b13efa51aa4d4d706e5630edc83c179c9abae02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b14dbb63c3a580fa166ac94e0e0a46fe434a8681894f6e0e4401792ea8b3c73 0.600000000000 1529416 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": 1058967, "vin": [ { "gen": { "height": 1058957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b14dbb63c3a580fa166ac94e0e0a46fe434a8681894f6e0e4401792ea8b3c73" } } ], "extra": [ 1, 182, 105, 117, 213, 70, 109, 99, 95, 78, 147, 15, 162, 122, 27, 19, 239, 165, 26, 164, 212, 215, 6, 229, 99, 14, 220, 131, 193, 121, 201, 171, 174, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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