Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e24931ce4d2409201d9c31164ce1e87155c59a0d1daf62a112e2c6d5b40848

Tx prefix hash: 4c5c7efd3f2d68d19d222fb2cc4aa8fdc9d6b792cd51a3311549ad50ce768ae2
Tx public key: 624369598a117922ed980cdba8a8a5fa2f4e72737f7d22e415c163d6131f2fd9
Timestamp: 1574731307 Timestamp [UCT]: 2019-11-26 01:21:47 Age [y:d:h:m:s]: 05:099:22:22:59
Block: 17563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214012 RingCT/type: yes/0
Extra: 01624369598a117922ed980cdba8a8a5fa2f4e72737f7d22e415c163d6131f2fd9021100000001f95225a5000000000000000000

1 output(s) for total of 536.793651171000 dcy

stealth address amount amount idx
00: fb22f1e8a4f5a314d75cba3fba072452603a92b1c9a25c0a4ff48beabdc5072e 536.793651171000 25715 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": 17573, "vin": [ { "gen": { "height": 17563 } } ], "vout": [ { "amount": 536793651171, "target": { "key": "fb22f1e8a4f5a314d75cba3fba072452603a92b1c9a25c0a4ff48beabdc5072e" } } ], "extra": [ 1, 98, 67, 105, 89, 138, 17, 121, 34, 237, 152, 12, 219, 168, 168, 165, 250, 47, 78, 114, 115, 127, 125, 34, 228, 21, 193, 99, 214, 19, 31, 47, 217, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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