Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668d69cea2b2218205ce0c9f91ebb1d4561c1c3efa3279e51a44091c42e14781

Tx prefix hash: f860735228dabeac13ea1f7b71f0ab9460c891c77583b70f63f98eadb6f6ecf5
Tx public key: 7f18cb0cbb522297aa470055edae73fc9ff4a2a15a1018e685f080f7c598d1b8
Timestamp: 1703208423 Timestamp [UCT]: 2023-12-22 01:27:03 Age [y:d:h:m:s]: 01:328:05:51:40
Block: 918343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493455 RingCT/type: yes/0
Extra: 017f18cb0cbb522297aa470055edae73fc9ff4a2a15a1018e685f080f7c598d1b802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3390a292d02e33ada23e392d211428044744602258e62b48ba9d41aa59cd729 0.600000000000 1375985 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": 918353, "vin": [ { "gen": { "height": 918343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3390a292d02e33ada23e392d211428044744602258e62b48ba9d41aa59cd729" } } ], "extra": [ 1, 127, 24, 203, 12, 187, 82, 34, 151, 170, 71, 0, 85, 237, 174, 115, 252, 159, 244, 162, 161, 90, 16, 24, 230, 133, 240, 128, 247, 197, 152, 209, 184, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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