Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b633f31c1904326d354f554ffa0123299c54bdb61b94bf1da8a38f8fd2432e

Tx prefix hash: 8c2a7531d38305541e8f9670e40bd274c90b19882cfc97a4f6a9defd2325f2de
Tx public key: 849bccae16708bccf132e8b284345cd1df37ccfb7a37e5ce8d221ad213f9629f
Timestamp: 1725981908 Timestamp [UCT]: 2024-09-10 15:25:08 Age [y:d:h:m:s]: 00:278:03:20:36
Block: 1107148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198567 RingCT/type: yes/0
Extra: 01849bccae16708bccf132e8b284345cd1df37ccfb7a37e5ce8d221ad213f9629f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30563f1d66d702865082d527a3e6ef58b6e0a8768a38be526bc7da1a01ec2a8 0.600000000000 1584755 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": 1107158, "vin": [ { "gen": { "height": 1107148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30563f1d66d702865082d527a3e6ef58b6e0a8768a38be526bc7da1a01ec2a8" } } ], "extra": [ 1, 132, 155, 204, 174, 22, 112, 139, 204, 241, 50, 232, 178, 132, 52, 92, 209, 223, 55, 204, 251, 122, 55, 229, 206, 141, 34, 26, 210, 19, 249, 98, 159, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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