Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93a90fd830853a2d1cb7f2bafdcffbd73bdea79af9c3f1d83a67038d6625c24d

Tx prefix hash: 206d0db42ce2973414f492de49d60eabd83f4f0be424193a3a96937093b3af63
Tx public key: 5fa6e4a54f9c280355e1e98a02dff33460b1edea12fb0345c52fba2b69328beb
Timestamp: 1712315930 Timestamp [UCT]: 2024-04-05 11:18:50 Age [y:d:h:m:s]: 00:326:01:18:10
Block: 993828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233107 RingCT/type: yes/0
Extra: 015fa6e4a54f9c280355e1e98a02dff33460b1edea12fb0345c52fba2b69328beb02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68213b9aeaaf18a86377d208ee1562be8c29b7de125ca55e80ba126eb62d8c4 0.600000000000 1454216 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": 993838, "vin": [ { "gen": { "height": 993828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68213b9aeaaf18a86377d208ee1562be8c29b7de125ca55e80ba126eb62d8c4" } } ], "extra": [ 1, 95, 166, 228, 165, 79, 156, 40, 3, 85, 225, 233, 138, 2, 223, 243, 52, 96, 177, 237, 234, 18, 251, 3, 69, 197, 47, 186, 43, 105, 50, 139, 235, 2, 17, 0, 0, 0, 6, 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