Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9980e20317cc3f350c93d3eb57f9876feeddd500e1ee66932806d1f6fc972294

Tx prefix hash: 67078246f11a727370e04529416d045ce4ae186d30c2b5e47f7c55f6899a1290
Tx public key: f89c0000e7f3eb7cf2b801a57ea3e12c7943f7698b9e01db4696d75aa7037a0a
Timestamp: 1723130812 Timestamp [UCT]: 2024-08-08 15:26:52 Age [y:d:h:m:s]: 00:196:17:57:47
Block: 1083513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140465 RingCT/type: yes/0
Extra: 01f89c0000e7f3eb7cf2b801a57ea3e12c7943f7698b9e01db4696d75aa7037a0a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d89845acc95739ab7f9c895e6fe04849a20de8c1c2fd1ebd76921ff91aa05500 0.600000000000 1557460 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": 1083523, "vin": [ { "gen": { "height": 1083513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d89845acc95739ab7f9c895e6fe04849a20de8c1c2fd1ebd76921ff91aa05500" } } ], "extra": [ 1, 248, 156, 0, 0, 231, 243, 235, 124, 242, 184, 1, 165, 126, 163, 225, 44, 121, 67, 247, 105, 139, 158, 1, 219, 70, 150, 215, 90, 167, 3, 122, 10, 2, 17, 0, 0, 0, 4, 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