Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2292ce53e526295bf943926185fd9f891b089b75170d8426950270fbbe9ab273

Tx prefix hash: e2a3c76f413498855368c916e9c6315a5bf8bfa88160b84db209699b4bac6691
Tx public key: 599ac8a216f138d6b4b6b09a42a3f1178d622fcdf03e76f83316c5e6af981821
Timestamp: 1725392647 Timestamp [UCT]: 2024-09-03 19:44:07 Age [y:d:h:m:s]: 00:221:07:30:07
Block: 1102270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158011 RingCT/type: yes/0
Extra: 01599ac8a216f138d6b4b6b09a42a3f1178d622fcdf03e76f83316c5e6af98182102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eb2b1289ede74e2fa2a67f1ef23455f3c3d58af11d5909a79f8a621dac1b841 0.600000000000 1578641 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": 1102280, "vin": [ { "gen": { "height": 1102270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eb2b1289ede74e2fa2a67f1ef23455f3c3d58af11d5909a79f8a621dac1b841" } } ], "extra": [ 1, 89, 154, 200, 162, 22, 241, 56, 214, 180, 182, 176, 154, 66, 163, 241, 23, 141, 98, 47, 205, 240, 62, 118, 248, 51, 22, 197, 230, 175, 152, 24, 33, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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