Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e964fb74a6477557da2879662e06ac746b8439a6ae79fbbfa1ad54e358be0bfe

Tx prefix hash: 6d0add80bab3f9985e946b523259970ec87a5373b37f04e6d3948a8d653af96a
Tx public key: b241b4d3e7dc5137d89c29a043ebed42efdbe5f4beb935928975d0c44dc30718
Timestamp: 1746401986 Timestamp [UCT]: 2025-05-04 23:39:46 Age [y:d:h:m:s]: 00:199:08:21:43
Block: 1275918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140187 RingCT/type: yes/0
Extra: 01b241b4d3e7dc5137d89c29a043ebed42efdbe5f4beb935928975d0c44dc307180211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5d5e81f2541974d53dda63e5dd408aa6a679ad5d216e7688cbee2e3927200b 0.600000000000 1763233 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": 1275928, "vin": [ { "gen": { "height": 1275918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5d5e81f2541974d53dda63e5dd408aa6a679ad5d216e7688cbee2e3927200b" } } ], "extra": [ 1, 178, 65, 180, 211, 231, 220, 81, 55, 216, 156, 41, 160, 67, 235, 237, 66, 239, 219, 229, 244, 190, 185, 53, 146, 137, 117, 208, 196, 77, 195, 7, 24, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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