Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac69b1ef3ea05a11f2fb1f24d8e10410cc078db5afd5f292a3769a1837fc33e

Tx prefix hash: aac58ef4847326ab64b99857c16d364009bb339c12604b4c0443a0fc37e168d1
Tx public key: 2ca99d297f086300d238623e55e5c09c9eca304c1bb60cb09591ab51cecef9f2
Timestamp: 1636710544 Timestamp [UCT]: 2021-11-12 09:49:04 Age [y:d:h:m:s]: 03:006:09:25:19
Block: 372715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 783164 RingCT/type: yes/0
Extra: 012ca99d297f086300d238623e55e5c09c9eca304c1bb60cb09591ab51cecef9f202110000000106faf294000000000000000000

1 output(s) for total of 35.730646474000 dcy

stealth address amount amount idx
00: 1d5a9175d0ab369b18c1537e51d6e96f20dd7bb16e9e7c7a75877ad911cf17d9 35.730646474000 754935 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": 372725, "vin": [ { "gen": { "height": 372715 } } ], "vout": [ { "amount": 35730646474, "target": { "key": "1d5a9175d0ab369b18c1537e51d6e96f20dd7bb16e9e7c7a75877ad911cf17d9" } } ], "extra": [ 1, 44, 169, 157, 41, 127, 8, 99, 0, 210, 56, 98, 62, 85, 229, 192, 156, 158, 202, 48, 76, 27, 182, 12, 176, 149, 145, 171, 81, 206, 206, 249, 242, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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