Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848070826c105de1d1a6d0dd61466063c2535e53f171ec661ad52a7aa20379e0

Tx prefix hash: aa9c9223b8133d7d0d3d142e95c2dbb1d2ee73e36057470bac7b5a8fab7181dd
Tx public key: 0fe91e7bd759c69e3355970a88e8d575fb8e58b32d7d7209e270ae72d8012bb5
Timestamp: 1637734529 Timestamp [UCT]: 2021-11-24 06:15:29 Age [y:d:h:m:s]: 02:347:05:14:39
Block: 380911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766141 RingCT/type: yes/0
Extra: 010fe91e7bd759c69e3355970a88e8d575fb8e58b32d7d7209e270ae72d8012bb502110000000537cb3088000000000000000000

1 output(s) for total of 33.565383786000 dcy

stealth address amount amount idx
00: 188679b120c4f4f5649cd486662826f0bfc33f5b91b5633fe64f9fe9506763af 33.565383786000 769683 of 0

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": 380921, "vin": [ { "gen": { "height": 380911 } } ], "vout": [ { "amount": 33565383786, "target": { "key": "188679b120c4f4f5649cd486662826f0bfc33f5b91b5633fe64f9fe9506763af" } } ], "extra": [ 1, 15, 233, 30, 123, 215, 89, 198, 158, 51, 85, 151, 10, 136, 232, 213, 117, 251, 142, 88, 179, 45, 125, 114, 9, 226, 112, 174, 114, 216, 1, 43, 181, 2, 17, 0, 0, 0, 5, 55, 203, 48, 136, 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