Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57ed8a0c307794878ba26a1151963551c2f001fd9ca5922f85c30711804c1ab7

Tx prefix hash: 4369f6e5749c5e9ba88ee3880c9ca14e8aff3a449e9aa17639ce7a52f9c9ac60
Tx public key: 83664755ed0cb0d51a1ce9ded9f633dd28e42ab9850e4fd51db83d8e76587a0f
Timestamp: 1686447806 Timestamp [UCT]: 2023-06-11 01:43:26 Age [y:d:h:m:s]: 01:305:02:05:26
Block: 779653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479221 RingCT/type: yes/0
Extra: 0183664755ed0cb0d51a1ce9ded9f633dd28e42ab9850e4fd51db83d8e76587a0f021100000003faf35c9c000000000000000000

1 output(s) for total of 1.602087092000 dcy

stealth address amount amount idx
00: 67f778e87bee8a501aa399505be80f625b178dfd868a8af78e2a9924a092e8eb 1.602087092000 1229322 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": 779663, "vin": [ { "gen": { "height": 779653 } } ], "vout": [ { "amount": 1602087092, "target": { "key": "67f778e87bee8a501aa399505be80f625b178dfd868a8af78e2a9924a092e8eb" } } ], "extra": [ 1, 131, 102, 71, 85, 237, 12, 176, 213, 26, 28, 233, 222, 217, 246, 51, 221, 40, 228, 42, 185, 133, 14, 79, 213, 29, 184, 61, 142, 118, 88, 122, 15, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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