Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5498c88b67de5fae69accc98a1e0b05d4dcf591803fb4012e2750155db9e592

Tx prefix hash: f3920cb7ca8a23a9ecad8c3464e15c29a8d52178add8045c884753ea2c634041
Tx public key: 74ba179364ad0f56d28d45a7eb007dafbaae0ae997ac072c2888d56feb120155
Timestamp: 1712353898 Timestamp [UCT]: 2024-04-05 21:51:38 Age [y:d:h:m:s]: 01:208:12:09:17
Block: 994134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407727 RingCT/type: yes/0
Extra: 0174ba179364ad0f56d28d45a7eb007dafbaae0ae997ac072c2888d56feb12015502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3551fd6e5ec4ca973f001ea5c1a19e7e51d391e9f423a659c90955c3ea3e028 0.600000000000 1454536 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": 994144, "vin": [ { "gen": { "height": 994134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3551fd6e5ec4ca973f001ea5c1a19e7e51d391e9f423a659c90955c3ea3e028" } } ], "extra": [ 1, 116, 186, 23, 147, 100, 173, 15, 86, 210, 141, 69, 167, 235, 0, 125, 175, 186, 174, 10, 233, 151, 172, 7, 44, 40, 136, 213, 111, 235, 18, 1, 85, 2, 17, 0, 0, 0, 1, 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