Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c641fd94fc30b167a39a006266e3e6eeef7c1d4314dfbadc5fdf1bc7829981

Tx prefix hash: 9f4cf2cb791f8b9ad3b5995f655a449cf710307961da26cad79197de27ce3962
Tx public key: 5ca684d9980bfb9f2c3e7068ee882cb876336f958fce091f2f694987bfe0308f
Timestamp: 1725787854 Timestamp [UCT]: 2024-09-08 09:30:54 Age [y:d:h:m:s]: 00:122:23:02:23
Block: 1105542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87930 RingCT/type: yes/0
Extra: 015ca684d9980bfb9f2c3e7068ee882cb876336f958fce091f2f694987bfe0308f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aabce85e0c96cee338fb3f583e35b09114348fad8eca877c33a3b9d9d5398b41 0.600000000000 1582905 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": 1105552, "vin": [ { "gen": { "height": 1105542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aabce85e0c96cee338fb3f583e35b09114348fad8eca877c33a3b9d9d5398b41" } } ], "extra": [ 1, 92, 166, 132, 217, 152, 11, 251, 159, 44, 62, 112, 104, 238, 136, 44, 184, 118, 51, 111, 149, 143, 206, 9, 31, 47, 105, 73, 135, 191, 224, 48, 143, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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