Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed0297ea1fbf25f5e40da7c9d2028b4951a4df41fc5fd11119dd8ee0c74aa547

Tx prefix hash: 5b2611298ecfb59e2dae16abe99bfbfabb979edcd195de4ad7bcecf1575859d9
Tx public key: f078491c3f42010efb7eeca80ad7180c6afb789518f1398ff1f4d5fe8c141568
Timestamp: 1735395390 Timestamp [UCT]: 2024-12-28 14:16:30 Age [y:d:h:m:s]: 00:360:00:31:55
Block: 1185055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254871 RingCT/type: yes/0
Extra: 01f078491c3f42010efb7eeca80ad7180c6afb789518f1398ff1f4d5fe8c1415680211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d38223d9a826ed49e0f40f3e9c4e20970064b8b4a4f7251377c91e23c249f98 0.600000000000 1671520 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": 1185065, "vin": [ { "gen": { "height": 1185055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d38223d9a826ed49e0f40f3e9c4e20970064b8b4a4f7251377c91e23c249f98" } } ], "extra": [ 1, 240, 120, 73, 28, 63, 66, 1, 14, 251, 126, 236, 168, 10, 215, 24, 12, 106, 251, 120, 149, 24, 241, 57, 143, 241, 244, 213, 254, 140, 20, 21, 104, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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