Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cfd5bd94987e6fc52b608b1ec14b4a638e5198b5253865b2b4f438870953cd2

Tx prefix hash: 11d4697d287c348e1de9cfdac32df4b327b5811f449a1ee69d356c6efd893310
Tx public key: 29cba02378f368beb7ff3d067a38f3a98a7ffecc42fc38212cf305ae10722d5e
Timestamp: 1755002858 Timestamp [UCT]: 2025-08-12 12:47:38 Age [y:d:h:m:s]: 00:107:17:34:52
Block: 1345469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76317 RingCT/type: yes/0
Extra: 0129cba02378f368beb7ff3d067a38f3a98a7ffecc42fc38212cf305ae10722d5e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7ce86b7e3414e373ba8a522dc1f4ca23d81f0b4b0467d3231c62c6dc68e4865 0.600000000000 1833362 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": 1345479, "vin": [ { "gen": { "height": 1345469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7ce86b7e3414e373ba8a522dc1f4ca23d81f0b4b0467d3231c62c6dc68e4865" } } ], "extra": [ 1, 41, 203, 160, 35, 120, 243, 104, 190, 183, 255, 61, 6, 122, 56, 243, 169, 138, 127, 254, 204, 66, 252, 56, 33, 44, 243, 5, 174, 16, 114, 45, 94, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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