Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91936747aad087e373c7255b4e75a0f978521a4f6e227d3a478d07a56e7d0e97

Tx prefix hash: 866c984686a1dbfc536373ddf48dcb1a0bb40408b33060fdcf8d871052b89fb8
Tx public key: 6d19a77fc41a03b05a995329c88ce21dac81ea97c258b599af9daf76cd18431a
Timestamp: 1720700447 Timestamp [UCT]: 2024-07-11 12:20:47 Age [y:d:h:m:s]: 00:286:22:25:27
Block: 1063366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205016 RingCT/type: yes/0
Extra: 016d19a77fc41a03b05a995329c88ce21dac81ea97c258b599af9daf76cd18431a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f90fd4f1a372afd7d61079d14b9dc9f4e440bc09da9fbec7e04ad939a78cc8 0.600000000000 1533881 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": 1063376, "vin": [ { "gen": { "height": 1063366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f90fd4f1a372afd7d61079d14b9dc9f4e440bc09da9fbec7e04ad939a78cc8" } } ], "extra": [ 1, 109, 25, 167, 127, 196, 26, 3, 176, 90, 153, 83, 41, 200, 140, 226, 29, 172, 129, 234, 151, 194, 88, 181, 153, 175, 157, 175, 118, 205, 24, 67, 26, 2, 17, 0, 0, 0, 9, 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