Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a275d08a90c67a05ad4c37476bae1629263a493ab50c008afdc02bd634d59d23

Tx prefix hash: 844eb67d93bccbed5c3bf0f84b85e1af96527ee866918c29fc7f977a0fda4f1a
Tx public key: 6f8a929947e01f21940007f897c0002182249c3d766ce335fd0a0f8a6027e3c5
Timestamp: 1626426044 Timestamp [UCT]: 2021-07-16 09:00:44 Age [y:d:h:m:s]: 03:216:13:22:35
Block: 295101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925677 RingCT/type: yes/0
Extra: 016f8a929947e01f21940007f897c0002182249c3d766ce335fd0a0f8a6027e3c502110000000a0f4c30de000000000000000000

1 output(s) for total of 64.596410005000 dcy

stealth address amount amount idx
00: 3998ef640bae9eff0a614388ce25a134368bb808269c5485db6da596f2953039 64.596410005000 618057 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": 295111, "vin": [ { "gen": { "height": 295101 } } ], "vout": [ { "amount": 64596410005, "target": { "key": "3998ef640bae9eff0a614388ce25a134368bb808269c5485db6da596f2953039" } } ], "extra": [ 1, 111, 138, 146, 153, 71, 224, 31, 33, 148, 0, 7, 248, 151, 192, 0, 33, 130, 36, 156, 61, 118, 108, 227, 53, 253, 10, 15, 138, 96, 39, 227, 197, 2, 17, 0, 0, 0, 10, 15, 76, 48, 222, 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