Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57ab8626a299486cdc877f38aa80ce644960b2ae4db7c99159df932576981295

Tx prefix hash: 7e0818a5b6cbacc1c1416d949f0386c543b91c2de25c915de092d0de4afd93e7
Tx public key: d8b5c0578bacd46e4c8ae6c235063974ac4054f3a8d37ae04fa2af5739e9c108
Timestamp: 1694398954 Timestamp [UCT]: 2023-09-11 02:22:34 Age [y:d:h:m:s]: 01:171:07:37:59
Block: 845480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383521 RingCT/type: yes/0
Extra: 01d8b5c0578bacd46e4c8ae6c235063974ac4054f3a8d37ae04fa2af5739e9c10802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.969558120000 dcy

stealth address amount amount idx
00: 197c69b0808fad9faaf1f9ef8f283fff5f46f9b181f3da4f22623a38c9c38d5e 0.969558120000 1298870 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": 845490, "vin": [ { "gen": { "height": 845480 } } ], "vout": [ { "amount": 969558120, "target": { "key": "197c69b0808fad9faaf1f9ef8f283fff5f46f9b181f3da4f22623a38c9c38d5e" } } ], "extra": [ 1, 216, 181, 192, 87, 139, 172, 212, 110, 76, 138, 230, 194, 53, 6, 57, 116, 172, 64, 84, 243, 168, 211, 122, 224, 79, 162, 175, 87, 57, 233, 193, 8, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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