Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd286751c56adccdb6bd20f201d4919c2fefee6a849e2856265f571e8cd3a2e0

Tx prefix hash: 63250c3720352557079bb6ab963efa436af47605846d09d3eb38f27601c53942
Tx public key: f48d883f513f42e9d35bc775aa1b7e45dda36dfa73f870c3b810fd053078f64d
Timestamp: 1719898323 Timestamp [UCT]: 2024-07-02 05:32:03 Age [y:d:h:m:s]: 00:347:04:56:13
Block: 1056716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248065 RingCT/type: yes/0
Extra: 01f48d883f513f42e9d35bc775aa1b7e45dda36dfa73f870c3b810fd053078f64d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c94634c4f1d4d52ae10fa0dd93d34f43c709213f7d6e47740e347a2db67d497 0.600000000000 1527135 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": 1056726, "vin": [ { "gen": { "height": 1056716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c94634c4f1d4d52ae10fa0dd93d34f43c709213f7d6e47740e347a2db67d497" } } ], "extra": [ 1, 244, 141, 136, 63, 81, 63, 66, 233, 211, 91, 199, 117, 170, 27, 126, 69, 221, 163, 109, 250, 115, 248, 112, 195, 184, 16, 253, 5, 48, 120, 246, 77, 2, 17, 0, 0, 0, 5, 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