Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f5447c584b62f8603b0dec4231c0900a3c7e87266a83039e96765969816c365

Tx prefix hash: a97de63ed2dc8701eb2efb59953c00d529e744939984254436649241d046bec1
Tx public key: b9f0fb9e6b925f4ec846ce2b1c38fc400ff9ab3906c3eae044579a7002821864
Timestamp: 1651822235 Timestamp [UCT]: 2022-05-06 07:30:35 Age [y:d:h:m:s]: 02:204:18:48:01
Block: 495383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 666436 RingCT/type: yes/0
Extra: 01b9f0fb9e6b925f4ec846ce2b1c38fc400ff9ab3906c3eae044579a70028218640211000000095eb576c5000000000000000000

1 output(s) for total of 14.014922161000 dcy

stealth address amount amount idx
00: b06159ac0d47f0c2db3a12f3159e55e121bca0c5ecd950a1ea4f17796482c81c 14.014922161000 919178 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": 495393, "vin": [ { "gen": { "height": 495383 } } ], "vout": [ { "amount": 14014922161, "target": { "key": "b06159ac0d47f0c2db3a12f3159e55e121bca0c5ecd950a1ea4f17796482c81c" } } ], "extra": [ 1, 185, 240, 251, 158, 107, 146, 95, 78, 200, 70, 206, 43, 28, 56, 252, 64, 15, 249, 171, 57, 6, 195, 234, 224, 68, 87, 154, 112, 2, 130, 24, 100, 2, 17, 0, 0, 0, 9, 94, 181, 118, 197, 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