Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8557273d883931100e30cd456a72014aba35b4458d312b31fbab4d32473b87e3

Tx prefix hash: d71e5ed111a1be33361fad0e347b1f6c4c82a7f072da98efd264d49352ddab75
Tx public key: 41a9e1061adc42a3a8b63b0e9caa8f794dba216811d8a0946a356019a17d6ccb
Timestamp: 1721318694 Timestamp [UCT]: 2024-07-18 16:04:54 Age [y:d:h:m:s]: 00:265:22:03:50
Block: 1068509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189955 RingCT/type: yes/0
Extra: 0141a9e1061adc42a3a8b63b0e9caa8f794dba216811d8a0946a356019a17d6ccb021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 141b3fa31ae6de7cc9c83af62b9e689e0d800c0b7846b9a4c5f84215bf481852 0.600000000000 1539588 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": 1068519, "vin": [ { "gen": { "height": 1068509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "141b3fa31ae6de7cc9c83af62b9e689e0d800c0b7846b9a4c5f84215bf481852" } } ], "extra": [ 1, 65, 169, 225, 6, 26, 220, 66, 163, 168, 182, 59, 14, 156, 170, 143, 121, 77, 186, 33, 104, 17, 216, 160, 148, 106, 53, 96, 25, 161, 125, 108, 203, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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