Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4285276c814eb60a6a87316736852fdfef6da487a14b47419267738d14fd9ae

Tx prefix hash: 391bc872dbf5eb535a982931e843f9257a769521f64ac05b9cb908da7ce47cbb
Tx public key: 01b5102b4e8c3d5f386195f83dda6f79017294f1d83f3b73ee10e19dc1a6b71f
Timestamp: 1739717650 Timestamp [UCT]: 2025-02-16 14:54:10 Age [y:d:h:m:s]: 00:277:07:33:49
Block: 1220553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195977 RingCT/type: yes/0
Extra: 0101b5102b4e8c3d5f386195f83dda6f79017294f1d83f3b73ee10e19dc1a6b71f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 200f57c6e9b2924388bfed8a154f8984f354611be1c3ee6bbc1eee8dab71c2ca 0.600000000000 1707394 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": 1220563, "vin": [ { "gen": { "height": 1220553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "200f57c6e9b2924388bfed8a154f8984f354611be1c3ee6bbc1eee8dab71c2ca" } } ], "extra": [ 1, 1, 181, 16, 43, 78, 140, 61, 95, 56, 97, 149, 248, 61, 218, 111, 121, 1, 114, 148, 241, 216, 63, 59, 115, 238, 16, 225, 157, 193, 166, 183, 31, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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