Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4a11a626255fa158ff9548dcd97acdea045f19ac3be427e004e1042d860234

Tx prefix hash: bb23173e1c5dfd13c41cee7a01ea10ccff90989642999b0df32e511d9059b1c2
Tx public key: 56eb1b4c4ea7c1d7bf0aed797a9122eceb18f57502f6cd7e0ee8a788f2d8f5f8
Timestamp: 1723330916 Timestamp [UCT]: 2024-08-10 23:01:56 Age [y:d:h:m:s]: 01:091:03:49:31
Block: 1085170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323624 RingCT/type: yes/0
Extra: 0156eb1b4c4ea7c1d7bf0aed797a9122eceb18f57502f6cd7e0ee8a788f2d8f5f8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c42fe41c35a95ed4548d2b3d5a55f475693936636c1920c495c1f8ddc386865 0.600000000000 1559695 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": 1085180, "vin": [ { "gen": { "height": 1085170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c42fe41c35a95ed4548d2b3d5a55f475693936636c1920c495c1f8ddc386865" } } ], "extra": [ 1, 86, 235, 27, 76, 78, 167, 193, 215, 191, 10, 237, 121, 122, 145, 34, 236, 235, 24, 245, 117, 2, 246, 205, 126, 14, 232, 167, 136, 242, 216, 245, 248, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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