Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3de1fd98ecfd4f585d4d98e0e26a4e1b22cae9d02e40bbb4d3607274991ccd

Tx prefix hash: 66a736662ba476cc86685bcf99641a17100f20c3e9007b87fed7320874ae2ede
Tx public key: f57d10b228cb7091bce8cc86dc7391b9f7181aa2af2eee5c26bb3185a8564d4e
Timestamp: 1719608899 Timestamp [UCT]: 2024-06-28 21:08:19 Age [y:d:h:m:s]: 00:299:16:46:01
Block: 1054309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214162 RingCT/type: yes/0
Extra: 01f57d10b228cb7091bce8cc86dc7391b9f7181aa2af2eee5c26bb3185a8564d4e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 864696daed87d780c2ab628eaf6cdbbbb3d20b01bc8639d3738901efdaa01646 0.600000000000 1524670 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": 1054319, "vin": [ { "gen": { "height": 1054309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "864696daed87d780c2ab628eaf6cdbbbb3d20b01bc8639d3738901efdaa01646" } } ], "extra": [ 1, 245, 125, 16, 178, 40, 203, 112, 145, 188, 232, 204, 134, 220, 115, 145, 185, 247, 24, 26, 162, 175, 46, 238, 92, 38, 187, 49, 133, 168, 86, 77, 78, 2, 17, 0, 0, 0, 4, 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