Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 505c70c5e9e1bfbbfc2322e5a4385dc4c52a5e30d52e84a36a8a6c861c0ad312

Tx prefix hash: 5864c8423fa174c084eebd31bc8955b5a2ad448d2a59d1885ca89f586d1fb053
Tx public key: 759553ae86633a800e472d7bc26b112a3f5af21d7ef37551018ec15b97b4046d
Timestamp: 1738901532 Timestamp [UCT]: 2025-02-07 04:12:12 Age [y:d:h:m:s]: 00:287:20:46:24
Block: 1213837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203481 RingCT/type: yes/0
Extra: 01759553ae86633a800e472d7bc26b112a3f5af21d7ef37551018ec15b97b4046d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8edec5c09ba02d4e716ea8f3c3e73dcd9656d7a8b22d321f62e55cdad4ef6993 0.600000000000 1700618 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": 1213847, "vin": [ { "gen": { "height": 1213837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8edec5c09ba02d4e716ea8f3c3e73dcd9656d7a8b22d321f62e55cdad4ef6993" } } ], "extra": [ 1, 117, 149, 83, 174, 134, 99, 58, 128, 14, 71, 45, 123, 194, 107, 17, 42, 63, 90, 242, 29, 126, 243, 117, 81, 1, 142, 193, 91, 151, 180, 4, 109, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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