Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7919db098a0269f506dd18ee0785c64bc5c12546e858baa3b3545cd531b92aa

Tx prefix hash: 5d34f24d9b2beed7ace096604858a7004d24b92cf40fb5cf2e61d2cb48a5c6d5
Tx public key: f3f93dcf72258fb6684486e5bfb6891bf17103f81933eea665c81f5b4b463d58
Timestamp: 1712204266 Timestamp [UCT]: 2024-04-04 04:17:46 Age [y:d:h:m:s]: 01:030:06:56:18
Block: 992896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282647 RingCT/type: yes/0
Extra: 01f3f93dcf72258fb6684486e5bfb6891bf17103f81933eea665c81f5b4b463d5802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 473c65c23596d39aa0f893b6744d96da8f6a73b8c751a03878207a930ea77cc1 0.600000000000 1453274 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": 992906, "vin": [ { "gen": { "height": 992896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "473c65c23596d39aa0f893b6744d96da8f6a73b8c751a03878207a930ea77cc1" } } ], "extra": [ 1, 243, 249, 61, 207, 114, 37, 143, 182, 104, 68, 134, 229, 191, 182, 137, 27, 241, 113, 3, 248, 25, 51, 238, 166, 101, 200, 31, 91, 75, 70, 61, 88, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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