Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e846cc5c77ea0bbad1940085e49caf31a362d1766a6459c3f766a7e8cf0fecb6

Tx prefix hash: bd02cf28275d6e32758b642d0627cd2f5cd3f9b574d7e7887f6aca0489cf3870
Tx public key: 3844136153b4b5543d482bf9ffda2f3a189de656e491887620d8f49b0b40c11c
Timestamp: 1705825482 Timestamp [UCT]: 2024-01-21 08:24:42 Age [y:d:h:m:s]: 00:355:18:21:11
Block: 940006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254724 RingCT/type: yes/0
Extra: 013844136153b4b5543d482bf9ffda2f3a189de656e491887620d8f49b0b40c11c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 659a9342d037caee03a24a1d267510aa2ddf50328cf66e44fc3bdfa6f3f9b294 0.600000000000 1398140 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": 940016, "vin": [ { "gen": { "height": 940006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "659a9342d037caee03a24a1d267510aa2ddf50328cf66e44fc3bdfa6f3f9b294" } } ], "extra": [ 1, 56, 68, 19, 97, 83, 180, 181, 84, 61, 72, 43, 249, 255, 218, 47, 58, 24, 157, 230, 86, 228, 145, 136, 118, 32, 216, 244, 155, 11, 64, 193, 28, 2, 17, 0, 0, 0, 1, 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