Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0cbbe5259b81e4f368828a191dfd3f6173ebcc9ef09f277c4c01ec0881fe779

Tx prefix hash: b68dddf67372f2f17d4bd03d608ad7e74384515e1fcbbf4ce490d284133f7d4a
Tx public key: 30eb7a3fef906d15a0f77b20a2d128a614f0d40d7f643656e734c58579ca7413
Timestamp: 1708922179 Timestamp [UCT]: 2024-02-26 04:36:19 Age [y:d:h:m:s]: 01:041:14:04:44
Block: 965726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290715 RingCT/type: yes/0
Extra: 0130eb7a3fef906d15a0f77b20a2d128a614f0d40d7f643656e734c58579ca741302110000001f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0d2f94c67471797628f6202f298553fbaecfbf842f4b8639948b41a0f21441e 0.600000000000 1425481 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": 965736, "vin": [ { "gen": { "height": 965726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0d2f94c67471797628f6202f298553fbaecfbf842f4b8639948b41a0f21441e" } } ], "extra": [ 1, 48, 235, 122, 63, 239, 144, 109, 21, 160, 247, 123, 32, 162, 209, 40, 166, 20, 240, 212, 13, 127, 100, 54, 86, 231, 52, 197, 133, 121, 202, 116, 19, 2, 17, 0, 0, 0, 31, 122, 156, 244, 199, 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